Skip to content

[TRTLLM-14715][feat] preserve native MoE A2A graph VAs across restore - #16632

Open
hhzhang16 wants to merge 14 commits into
NVIDIA:mainfrom
hhzhang16:hannahz/dep-1082-port-flashinfer-stable-va-lifecycle-for-native-moe-all-to
Open

[TRTLLM-14715][feat] preserve native MoE A2A graph VAs across restore#16632
hhzhang16 wants to merge 14 commits into
NVIDIA:mainfrom
hhzhang16:hannahz/dep-1082-port-flashinfer-stable-va-lifecycle-for-native-moe-all-to

Conversation

@hhzhang16

@hhzhang16 hhzhang16 commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Added checkpoint preparation and restoration for MNNVL-backed MoE communication.
  • Preserved native MoE A2A graph virtual addresses across workspace remapping.
  • Added shared workspace lifecycle management, bounded collectives, timeout handling, cleanup, and fail-closed restore behavior.
  • Rejected unsupported context-parallel Helix mappings and unmapped workspace access.
  • Added sleep/wakeup coordination for MNNVL resources.
  • Added lifecycle, CUDA-graph, failure-injection, workspace, communication-strategy, and RPC guard tests.

Dev Engineer Review

  • Centralized MNNVL allocation, mapping, cleanup, checkpoint, and restore logic.
  • Validated communicator compatibility and restored original virtual addresses.
  • Applied mapped-state checks before MoE workspace access.
  • Added consistent checkpoint APIs across MNNVL memory, MoE, All-to-All, and NVLink classes.
  • Prevented unsupported Helix configurations before workspace allocation.
  • Test-list entries target the A10, GB200, and CPU suites.
  • Helper CI jobs passed, but the related L0_MergeRequest_PR pipelines failed. Failed tests require review and a new CI run.
  • Shared lifecycle and failure-handling changes remain under separate review.

QA Engineer Review

  • Added lifecycle tests in tests/unittest/_torch/test_mnnvl_memory_lifecycle.py.
  • Added shared workspace tests in tests/unittest/_torch/test_mnnvl_alltoall_workspace.py.
  • Added three MNNVL checkpoint tests in TestMoEComm.
  • Added unsupported-Helix tests in test_communication_factory.py.
  • Expanded sleep/wakeup tests in test_sleep_collective_rpc_guards.py.
  • Added lifecycle coverage to tests/integration/test_lists/test-db/l0_a10.yml.
  • Added MoE checkpoint coverage to tests/integration/test_lists/test-db/l0_gb200_multi_gpus.yml.
  • Added sleep/wakeup guard coverage to tests/integration/test_lists/test-db/l0_cpu.yml.
  • Verdict: needs follow-up.

Description

This change ports the FlashInfer stable-VA lifecycle to TensorRT-LLM's native MoE all-to-all resources. FlashInfer implemented this lifecycle for its TRT-LLM-style MoE all-to-all workspace in flashinfer-ai/flashinfer#3727.

Test Coverage

PR Checklist

Please review the following before submitting your PR:

  • PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.

  • PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.

  • Test cases are provided for new code paths (see test instructions)

  • If PR introduces API changes, an appropriate PR label is added - either api-compatible or api-breaking. For api-breaking, include BREAKING in the PR title.

  • Any new dependencies have been scanned for license and vulnerabilities

  • CODEOWNERS updated if ownership changes

  • Documentation updated as needed

  • Update tava architecture diagram if there is a significant design change in PR.

  • The reviewers assigned automatically/manually are appropriate for the PR.

  • Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

To see a list of available CI bot commands, please comment /bot help.

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

MNNVL memory now supports bounded checkpoint detachment and restoration with lifecycle tracking and cleanup. Shared MoE workspaces coordinate mapped state, watchdogs, and checkpoint operations. Executor sleep-wakeup flows coordinate these hooks across ranks and handle partial failures.

Changes

MNNVL checkpoint lifecycle

Layer / File(s) Summary
Allocation records and handle mapping
tensorrt_llm/_mnnvl_utils.py
Allocation records track lifecycle and communicator metadata. Handle mapping uses bounded collectives and cleans up partial resources.
Memory teardown and checkpoint state
tensorrt_llm/_mnnvl_utils.py
Teardown preserves virtual-address reservations. Checkpoint restore validates communicator layout, remaps original addresses, and rolls back failures.
Shared workspace lifecycle and backend integration
tensorrt_llm/_torch/mnnvl_alltoall_workspace.py, tensorrt_llm/_torch/distributed/moe_alltoall.py, tensorrt_llm/_torch/modules/fused_moe/communication/*
Communication wrappers share workspace ownership, metadata, watchdogs, checkpoint state, cleanup, and mapped-state checks. CP-Helix mappings are rejected.
Sleep-wakeup checkpoint coordination
tensorrt_llm/_torch/pyexecutor/py_executor.py, tensorrt_llm/executor/base_worker.py
Executor coordination detects MNNVL resources, orders peer commits, runs checkpoint hooks around VMM operations, and propagates failures.
Checkpoint validation and test coverage
tests/unittest/_torch/test_mnnvl_memory_lifecycle.py, tests/unittest/_torch/test_mnnvl_alltoall_workspace.py, tests/unittest/_torch/modules/moe/*, tests/unittest/executor/test_sleep_collective_rpc_guards.py, tests/integration/test_lists/test-db/*
Tests cover cleanup, rollback, stable graph addresses, workspace lifecycle, Helix rejection, executor coordination, and bounded collective failures.

Estimated code review effort: 4 (Complex) | ~60 minutes

Merge Risk: 🟠 High · up to 5665e

This PR changes checkpoint/restore and distributed sleep/wakeup handling for native MoE communication resources. The current head still contains failure-path and resource-lifecycle issues that can unnecessarily stop workers, disturb shared distributed state, or retain stale mappings across restore, with an additional test-flakiness concern. The correctness issues should be fixed or explicitly accepted by the owners before merge.

Sequence Diagram(s)

sequenceDiagram
  participant BaseWorker
  participant PyExecutor
  participant WorkspaceLifecycle
  participant MnnvlMemory
  participant Communicator
  BaseWorker->>PyExecutor: PREPARE sleep or wakeup
  PyExecutor->>WorkspaceLifecycle: detect MNNVL resources
  BaseWorker->>Communicator: send peer COMMIT
  PyExecutor->>WorkspaceLifecycle: checkpoint_prepare()
  WorkspaceLifecycle->>MnnvlMemory: detach workspace handles
  BaseWorker->>PyExecutor: release or materialize VMM memory
  PyExecutor->>WorkspaceLifecycle: checkpoint_restore(comm)
  WorkspaceLifecycle->>MnnvlMemory: remap workspace handles
  WorkspaceLifecycle->>Communicator: validate restore readiness
  WorkspaceLifecycle-->>PyExecutor: reset communication state
Loading
🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description states the primary change but leaves Test Coverage empty and does not document checklist decisions for the substantial lifecycle and API changes. List the relevant unit and integration tests, and complete the applicable checklist items, including API compatibility, documentation, and CI status.
Docstring Coverage ⚠️ Warning Docstring coverage is 22.44% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the ticket, feature type, and primary change: preserving native MoE A2A graph virtual addresses across restore.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py (1)

703-722: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider mirroring the _require_mapped() guard here for cross-implementation consistency.

MoeAlltoAll.get_combine_payload_tensor_in_workspace() calls self._require_mapped() before the phase check, but this NVLink one-sided variant does not. In practice the phase != "dispatched" guard already blocks reaching this while handles are detached (checkpointing requires the idle phase), so this is a defense-in-depth consistency nit rather than a live bug. Aligning both keeps the two frontends symmetric if the phase semantics ever change.

♻️ Optional consistency tweak
     def get_combine_payload_tensor_in_workspace(
         self, runtime_max_tokens_per_rank: int, hidden_size: int, dtype: torch.dtype
     ) -> torch.Tensor:
         ...
+        self._require_mapped()
         if self._dispatch_state.get("phase") != "dispatched":
             raise RuntimeError(
                 "get_combine_payload_tensor_in_workspace called before a successful dispatch"
             )
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py`
around lines 703 - 722, Update get_combine_payload_tensor_in_workspace to call
the existing _require_mapped() guard before checking the dispatch phase,
matching MoeAlltoAll’s implementation while preserving the current phase
validation and behavior.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py`:
- Around line 703-722: Update get_combine_payload_tensor_in_workspace to call
the existing _require_mapped() guard before checking the dispatch phase,
matching MoeAlltoAll’s implementation while preserving the current phase
validation and behavior.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: bc5812ec-a3d9-4c6c-9695-5f1fa61aa472

📥 Commits

Reviewing files that changed from the base of the PR and between 445742c and 297d098.

📒 Files selected for processing (5)
  • tensorrt_llm/_mnnvl_utils.py
  • tensorrt_llm/_torch/distributed/moe_alltoall.py
  • tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py
  • tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_two_sided.py
  • tests/unittest/_torch/test_mnnvl_memory_lifecycle.py

@chienchunhung chienchunhung left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this. I left two lifecycle questions inline.

Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
Comment thread tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py Outdated
Comment thread tensorrt_llm/_torch/distributed/moe_alltoall.py Outdated
Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
@Funatiq Funatiq changed the title [None][feat] preserve native MoE A2A graph VAs across restore [TRTLLM-14715][feat] preserve native MoE A2A graph VAs across restore Jul 28, 2026
@chienchunhung
chienchunhung self-requested a review July 31, 2026 00:51
Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
Comment thread tests/unittest/_torch/test_mnnvl_memory_lifecycle.py
Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
Comment thread tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py Outdated
Comment thread tensorrt_llm/_torch/distributed/moe_alltoall.py Outdated
@hhzhang16

Copy link
Copy Markdown
Contributor Author

@chienchunhung A lot of your requests are intentionally isolated in hhzhang16#1 so the shared lifecycle and failure-handling changes can be reviewed there first. Then I’ll merge them into #16632.

@brnguyen2 brnguyen2 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The VA-preservation design looks correct: metainfo is a CPU offsets tensor (CHECK_CPU in moeAlltoAllOp.cpp), so the equality-check-then-swap after restore is safe for captured graphs, and the new barrier before closing exported fds in the POSIX-fd path is the right fix for the fd lifetime (which the old code handled by leaking the fds).

A few things beyond the inline comments:

  • No in-tree caller. checkpoint_prepare/checkpoint_restore are added but nothing invokes them. Please state in the description where the orchestration lands (follow-up PR? external framework?), and document the comm parameter contract on the public methods — it must be an mpi4py-like object with Get_rank/Get_size/barrier, matching the original allocation's rank and size, called symmetrically on every rank after all in-flight dispatch/combine pairs have completed.
  • Test Coverage section is empty. The new unit tests are mock-based and don't exercise the real collective detach/remap; please note whether a multi-GPU test (even a manual one) validated an actual unmap → remap → dispatch/combine → graph-replay cycle.
  • The description doesn't mention the two-sided behavioral change (combine now clears _dispatch_state) — worth a sentence, see inline.
  • MoeAlltoAll.checkpoint_restore and NVLinkOneSided.checkpoint_restore are ~30 near-identical lines. The files already carry a "can we avoid this duplication" TODO for _init_constants; consider a shared helper rather than growing the duplication.

Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
Comment thread tests/unittest/_torch/test_mnnvl_memory_lifecycle.py
@hhzhang16
hhzhang16 requested review from a team as code owners August 12, 2026 22:30
hhzhang16 added a commit to hhzhang16/TensorRT-LLM that referenced this pull request Aug 12, 2026
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
tests/unittest/_torch/test_mnnvl_memory_lifecycle.py (1)

290-349: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Add direct coverage for the new MnnvlMoe lifecycle statics.

The tests cover MnnvlMemory and the two communication wrappers. They never call the real MnnvlMoe.checkpoint_prepare, MnnvlMoe.checkpoint_restore, or MnnvlMoe.require_mapped. Line 339 replaces require_mapped with a Mock, so its logic stays untested.

Three branches in tensorrt_llm/_mnnvl_utils.py lines 655-685 have no coverage: the None guard for each workspace, the conditional moe_initialize_workspace call when moe_workspace_tensor is set, and the per-workspace mapped check. Monkeypatched workspace mocks are enough, matching the pattern at lines 302-304.

💚 Suggested additional tests
def test_moe_require_mapped_rejects_detached_prepare_workspace(monkeypatch):
    monkeypatch.setattr(mnnvl.MnnvlMoe, "moe_workspace", Mock(mapped=True))
    monkeypatch.setattr(mnnvl.MnnvlMoe, "moe_prepare_workspace", Mock(mapped=False))

    with pytest.raises(RuntimeError, match="workspace handles are unmapped"):
        mnnvl.MnnvlMoe.require_mapped()


def test_moe_checkpoint_prepare_skips_unallocated_workspaces(monkeypatch):
    workspace = Mock(mapped=True)
    monkeypatch.setattr(mnnvl.MnnvlMoe, "moe_workspace", workspace)
    monkeypatch.setattr(mnnvl.MnnvlMoe, "moe_prepare_workspace", None)

    mnnvl.MnnvlMoe.checkpoint_prepare()

    workspace.checkpoint_prepare.assert_called_once_with()
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/unittest/_torch/test_mnnvl_memory_lifecycle.py` around lines 290 - 349,
Add direct tests for MnnvlMoe.checkpoint_prepare, MnnvlMoe.checkpoint_restore,
and MnnvlMoe.require_mapped using monkeypatched workspace objects. Cover None
workspaces, conditional moe_initialize_workspace when moe_workspace_tensor is
set, per-workspace mapped validation, and delegation to checkpoint methods;
remove the require_mapped mock in
test_two_sided_combine_requires_new_prepare_before_next_dispatch so the real
logic is exercised.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tests/unittest/_torch/modules/moe/test_moe_comm.py`:
- Around line 2562-2665: Wrap the main execution of
_worker_mnnvl_checkpoint_graph_replay in a try/finally block so
communication.destroy() always runs, including assertion and MPI worker
failures. Keep the existing conditional destroy operation in the finally block,
ensuring persistent worker state is reset before reuse.

---

Nitpick comments:
In `@tests/unittest/_torch/test_mnnvl_memory_lifecycle.py`:
- Around line 290-349: Add direct tests for MnnvlMoe.checkpoint_prepare,
MnnvlMoe.checkpoint_restore, and MnnvlMoe.require_mapped using monkeypatched
workspace objects. Cover None workspaces, conditional moe_initialize_workspace
when moe_workspace_tensor is set, per-workspace mapped validation, and
delegation to checkpoint methods; remove the require_mapped mock in
test_two_sided_combine_requires_new_prepare_before_next_dispatch so the real
logic is exercised.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 67f3bd11-420a-4d0a-8066-3f4df3d96857

📥 Commits

Reviewing files that changed from the base of the PR and between ec3e1a1 and 300e0c4.

📒 Files selected for processing (8)
  • tensorrt_llm/_mnnvl_utils.py
  • tensorrt_llm/_torch/distributed/moe_alltoall.py
  • tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py
  • tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_two_sided.py
  • tests/integration/test_lists/test-db/l0_a10.yml
  • tests/integration/test_lists/test-db/l0_gb200_multi_gpus.yml
  • tests/unittest/_torch/modules/moe/test_moe_comm.py
  • tests/unittest/_torch/test_mnnvl_memory_lifecycle.py
🚧 Files skipped from review as they are similar to previous changes (3)
  • tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_one_sided.py
  • tensorrt_llm/_torch/distributed/moe_alltoall.py
  • tensorrt_llm/_torch/modules/fused_moe/communication/nvlink_two_sided.py

Comment thread tests/unittest/_torch/modules/moe/test_moe_comm.py Outdated

@brnguyen2 brnguyen2 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving — the comments below are optional touch-ups, not blockers.

Two description notes:

  • The new checkpoint_prepare/checkpoint_restore surface has no in-tree caller — it's staged infrastructure for an external fault-tolerance orchestrator (per the FlashInfer port). Please name the intended consumer/orchestration path in the description, and fill in the template's "Test Coverage" section (the CodeRabbit block lists the tests, but the template section is what release tooling and future readers scan).
  • An incidental behavior change worth a line in the description: the non-fabric path now closes pidfds, imported fds, and the exported fd on the success path (previously they leaked), which is why the new comm.barrier() after the pidfd_getfd loop is required — peers must finish duplicating an exported fd before its owner closes it. Both look correct; just make it explicit that the barrier is intentional.

Everything from the earlier review rounds (guarded fd closes, restored EPERM/ENOSYS hints, the cls.comm intent comment, the dispatch-after-combine regression test) is verified addressed on the current head.

Comment thread tensorrt_llm/_torch/distributed/moe_alltoall.py Outdated
Comment thread tensorrt_llm/_mnnvl_utils.py Outdated
@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #67963 [ run ] triggered by Bot. Commit: ac64583 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #67963 [ run ] completed with state SUCCESS. Commit: ac64583
/LLM/main/L0_MergeRequest_PR pipeline #55419 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@chienchunhung

Copy link
Copy Markdown
Collaborator

/bot run --disable-fail-fast

1 similar comment
@chienchunhung

Copy link
Copy Markdown
Collaborator

/bot run --disable-fail-fast

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68367 [ run ] triggered by Bot. Commit: ac64583 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68367 [ run ] completed with state SUCCESS. Commit: ac64583
/LLM/main/L0_MergeRequest_PR pipeline #55800 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@chienchunhung

Copy link
Copy Markdown
Collaborator

/bot run --disable-fail-fast

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68408 [ run ] triggered by Bot. Commit: 77b9b43 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68408 [ run ] completed with state ABORTED. Commit: 77b9b43

Link to invocation

@chienchunhung

Copy link
Copy Markdown
Collaborator

/bot run --disable-fail-fast

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68838 [ run ] triggered by Bot. Commit: 94eeb20 Link to invocation

Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
@hhzhang16
hhzhang16 force-pushed the hannahz/dep-1082-port-flashinfer-stable-va-lifecycle-for-native-moe-all-to branch from 94eeb20 to 711bad5 Compare August 24, 2026 20:04
@chienchunhung

Copy link
Copy Markdown
Collaborator

/bot run --disable-fail-fast

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68887 [ run ] triggered by Bot. Commit: 711bad5 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68838 [ run ] completed with state ABORTED. Commit: 94eeb20

Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #68887 [ run ] completed with state SUCCESS. Commit: 711bad5
/LLM/main/L0_MergeRequest_PR pipeline #56273 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants